Associating software with hardware using cryptography

ABSTRACT

Techniques for associating software with hardware using cryptography are described. The software is identified by a software identifier (ID), and the hardware is identified by a hardware ID. The software is hashed to obtain a code digest. A code signature is generated for the code digest, software ID, and hardware ID. A code image is formed with the software, software ID, code signature, and a certificate. The certificate contains cryptographic information used to authenticate the certificate and validate the code signature. The code image is loaded onto a device. The device validates the software to hardware association prior to executing the software. For the validation, the device authenticates the certificate with a certificate authority public key embedded within the device. The device also validates the code signature using the cryptographic information contained in the certificate, information in the code image, and the hardware ID embedded within the device.

This application claims the benefit of provisional U.S. application Ser. No. 60/461,341 (Attorney Docket No. 030282P), entitled “Associating Authenticated Software with a Licensed Hardware platform,” filed Apr. 8, 2003.

BACKGROUND

I. Field

The present invention relates generally to electronics, and more specifically to techniques for associating software with hardware.

II. Background

Electronics devices are widely available for various applications such as wireless communication, personal computing, and so on. These devices can support more functions and/or more complicated functions as the hardware becomes more powerful. For example, a modern-day cellular phone can provide wireless communication and may further function as a gaming device, a personal digital assistant (PDA), a digital camera, and so on.

A complex electronics device (e.g., a cellular phone) typically requires software to control the hardware and to support various designed functions. The software may be loaded into a non-volatile memory within the device during manufacturing and/or downloaded to the device during activation. Regardless of how the software is loaded onto the device, it may be desirable or necessary to ascertain whether or not the loaded software is “suitable” for the hardware, where suitability may be quantified by various factors as described below. For example, it may be desirable to ascertain that the loaded software is a version that has been authorized by the manufacturer and to prevent execution of the software if it is an unauthorized version.

There is therefore a need in the art for techniques to associate software with hardware for an electronics device.

SUMMARY

Techniques for associating software with hardware using cryptography are described herein. The software is identified by a software identifier (ID), which may be a software release version number. The hardware is identified by a hardware ID, which may be a model number or a part number.

In one specific scheme for associating software with hardware, the software is first hashed to obtain a code digest. A code signature is then generated for the code digest, the software ID, and the hardware ID. A code image is next formed with the software, the software ID, the code signature, and a certificate. The certificate contains cryptographic information used to (1) authenticate a certificate authority that generated the code signature and (2) validate the code signature. The code image is provided to and stored by a device, e.g., a wireless device such as a cellular phone.

The device validates the software to hardware association prior to executing the software. The device may perform the validation each time it is powered on. For the validation, the device first authenticates the certificate with a public key for the certificate authority, which is embedded within the device. The device then validates the code signature using (1) the cryptographic information contained in the certificate, (2) information in the code image, and (3) the hardware ID embedded within the device. The validation may also be performed in a different order (e.g., validate the signature first, then authenticate the certificate).

Various aspects and embodiments of the invention are described in further detail below.

BRIEF DESCRIPTION OF THE DRAWINGS

The features and nature of the present invention will become more apparent from the detailed description set forth below when taken in conjunction with the drawings in which like reference characters identify correspondingly throughout and wherein:

FIG. 1 shows a setup with various entities functioning to associate software with hardware;

FIG. 2 illustrates a code image that is sent to and stored by a wireless device;

FIG. 3 shows the processing to generate the code image for the software;

FIG. 4 shows a unit for generating a code signature;

FIG. 5 shows a unit for generating a digest used for the code signature;

FIG. 6 shows a process for generating the code image for the software;

FIG. 7 shows a process for generating the code signature;

FIG. 8 shows a block diagram of a code generator entity, a certificate authority, and the wireless device;

FIG. 9 shows a unit for validating the software based on the code signature; and

FIG. 10 shows a process for validating the software by the wireless device.

DETAILED DESCRIPTION

The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any embodiment or design described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments or designs.

The techniques described herein for associating software with hardware using cryptography may be used for various electronics devices such as a wireless device, a cellular phone, a handset, a computing device, a PDA, and so on. For clarity, these techniques are specifically described for a wireless device (e.g., a cellular phone).

The association of software with hardware is achieved using cryptographic techniques. In general, symmetric or asymmetric cryptography may be used for the association. For asymmetric cryptography (which is also known as public-key cryptography), a pair of keys composed of a private key and a public key is used for secure functions such as authentication, encryption, and decryption. The private key is kept in secrecy and the public key is provided as needed. Different secure functions may be achieved based on how the keys are used to process data. For symmetric cryptography (which is also known as secret key cryptography), both transacting entities know a secret key a priori and keep the key secret from other entities. Asymmetric cryptography is more suitable for applications in which one entity signs data and many entities authenticate the signature to validate the data. Thus, asymmetric cryptography is used for the following description.

FIG. 1 shows a setup 100 with various entities functioning to associate software with hardware. A code generator entity 10 generates software code 112 for a particular hardware platform (or simply, “hardware”). The software code is intended to be executed by the hardware to implement the desired functions. The software code is assigned a software identifier (ID), which may be a software release version number, a product key, or some other identification information. The hardware may be an integrated circuit, a chip set, a module, a device, and so on. The hardware is similarly assigned a hardware ID, which may be a model number, a product number, and so on. Each different hardware platform is assigned a different hardware ID, but all instances or units of the same hardware platform have the same hardware ID. Similarly, each software release is assigned a different software ID, but all instances or copies of the same software release have the same software ID. The software ID and hardware ID thus identify the software release and hardware platform, respectively, and not specific instances of the software and hardware.

Code generator entity 110 processes (e.g., hashes) the software code to obtain a code digest, which is a message digest resulting from the hashing. The hashing maps a potentially large and variable-sized file for the software code to a short fixed-size digest that can be more conveniently transferred and operated upon. Code generator entity 110 sends to a certificate authority (CA) 120 a request for a signature for the software code. The request includes (1) the code digest, (2) the software ID for the software code, and (3) the hardware ID for the hardware on which the software code is intended to run. The request may include equivalent information. For example, code generator entity 110 may send the software code instead of the code digest, some other information identifying the software code and the intended hardware, and so on.

Certificate authority 120 is a trusted entity that verifies whether or not the software can be associated with the hardware. Certificate authority 120 may first authenticate code generator entity 110 based on a certificate sent along with the request by code generator entity 110. This certificate is not shown in FIG. 1 for simplicity. The verification for the requested association may be achieved by matching the software ID and the hardware ID received from code generator entity 110 against information stored in a configuration table 122. For example, table 122 may store a list of software and hardware associations that is permitted for code generator entity 110. The requested association would be allowed if it matches one of the permitted associations stored in the table. Once the requested association has been verified, certificate authority 120 associates the software with the hardware using cryptography and crypto keys 124. Crypto keys 124 include two sets of keys: (1) a set of private and public keys used for signing and authenticating the software code (which are referred to herein as the “code” private and public keys) and (2) a set of private and public keys used for identifying and authenticating certificate authority 120 (which are referred to herein as the “CA” private and public keys). Certificate authority 120 generates a signature over the code digest, the software ID, and the hardware ID using the code private key. This signature is referred to herein as the “code signature”. Certificate authority 120 then sends the code signature and a certificate 126 to code generator entity 110. The certificate contains (1) the code public key corresponding to the code private key used to generate the code signature, (2) a signature generated over the code public key using the CA private key (which is referred to herein as the “CA signature”), and (3) possibly other information.

Code generator entity 110 receives the code signature and the certificate from certificate authority 120 and forms a code image with the software code, the software ID, the code signature, and the certificate. Code generator entity 110 thereafter sends the code image to a wireless device 130, which stores the image in a non-volatile memory 132. Device 130 has a boot code 134 that executes, for example, each time the device is powered on. The boot code validates the software code for execution by device 130 based on (1) the software ID, the code signature, and the certificate included in the code image, (2) hardware ID 136, and (3) CA public key 138, as described below. The boot code, hardware ID, and CA public key are embedded within device 130 and are tamper resistant. Device 130 only executes the software code if it is validated by the boot code.

Code generator entity 110 may be the manufacturer of wireless device 130, a network operator or service provider for a wireless communication network in which wireless device 130 is used, a third party software vendor, an original equipment manufacturer (OEM), a licensee of an entity with intellectual property rights to the hardware and/or the technology used for the communication network, or some other entity. Certificate authority 120 may be an independent entity (e.g., Geotrust, Verisign, and so on) that is trusted to perform the association of software with hardware. Certificate authority 120 and code generator entity 110 may also be parts of the same entity (e.g., a network operator).

FIG. 2 illustrates the code image that is sent to and stored by wireless device 130. The code image contains a field 212 for the software code, a field 214 for the software ID (SW ID), a field 216 for the code signature generated by certificate authority 120, and a field 218 for the certificate provided by certificate authority 120. The code image may be stored in various formats such as, for example, a format defined by a document RFC 2315, entitled “PKCS #7: Cryptographic Message Syntax Version 1.5,” which is publicly available. (PKCS stands for Public-Key Cryptography Standards.) The code image may also contain additional and/or different information than that shown in FIG. 2. For example, the software ID may be included within the software code and may not need to be stored separately as shown in FIG. 2.

FIG. 3 shows the processing to generate the code image for the software code. A hash function 310 receives and hashes the software code and provides the code digest. Since the software code may be a large file of many mega-bytes, the hashing generates a short fixed-size digest that can be more conveniently sent and operated upon. Hash function 310 maps the software code to the corresponding code digest. An important property of hash function 310 is to be collision resistance, which means that it should be infeasible to find two messages x and x′ that map to the same digest. Hash function 310 may be implemented with various cryptographic hash functions such as SHA-1 (Secure Hash Algorithm), MD-5 (Message Digest), and other hash algorithms known in the art. SHA-1 provides a 160-bit message digest and is described in Federal Information Processing Standard (FIPS) PUB 180-1, entitled “Secure Hash Standard,” which is publicly available. MD-5 provides a 128-bit message digest and is described in a document RFC 1321, entitled “The MD5 Message-Digest Algorithm,” which is also publicly available.

A sign function 320 receives the code digest, the software ID, the hardware ID, and the code private key. Sign function 320 generates the code signature based on (and over) the code digest, software ID, and hardware ID using the code private key. Sign function 320 may be implemented as described below.

A certificate generator 330 receives the code public key corresponding to the code private key, the CA private key, and other pertinent information (e.g., information identifying the entity generating the certificate, the cryptographic algorithms used for the certificate, and so on). Certificate generator 330 generates a signature over the code public key and the other pertinent information with the CA private key. This signature is referred to herein as the “CA signature”. Certificate generator 330 then forms the certificate with the code public key, the CA signature, and other information. The certificate may be stored in various formats such as, for example, a format defined by a document RFC 2459, entitled “Internet X.509 Public Key Infrastructure Certificate and CRL Profile,” which is publicly available. The certificate is used to authenticate certificate authority 120 as well as the code public key, as described below.

A combine unit 340 receives and combines the software code, the software ID, the code signature, and the certificate to obtain the code image (e.g., in PKCS #7 format).

Hash function 310 and combine unit 340 may reside at code generator entity 110 in FIG. 1. Sign function 320 and certificate generator 330 may reside at certificate authority 120. Alternatively, hash function 310, sign function 320, certificate generator 330, and combine unit 340 may all reside within the same entity.

FIG. 4 shows a processing unit 320 a for generating the code signature. Processing unit 320 a may be used for sign function 320 in FIG. 3.

Within unit 320 a, a hash unit 410 performs concatenation and hashing of the code digest, the software ID, and the hardware ID. For the embodiment shown in FIG. 4, within hash unit 410, a concatenate unit 412 receives and concatenates the code digest, the software ID, and the hardware ID to obtain a message (M). A hash function 414 hashes the message (M) and provides a message digest (D). Digest (D) contains information associating the software with the hardware and is referred to herein as the “signature digest”. An encryption unit 420 then encrypts the signature digest (D) with the code private key to generate the code signature (S).

Typically, the entire message used to generate the digest (D) is also sent along with the code signature (S). However, for this application, the three pieces of information used to obtain the code signature are available to the wireless device via other means. In particular, the wireless device can obtain the code digest and the software ID from the code image, and the hardware ID is embedded within the wireless device.

Unit 320 a may implement the RSA (Rivest, Shamir, and Adleman) algorithm. For this implementation, hash function 414 may implement SHA-1, MD-5, or some other hash function, and encryption unit 420 encrypts the digest (D) with the code private key. Unit 320 a may also implement the Digital Signature Standard (DSS) described in FIPS PUB 186, entitled “Digital Signature Standard (DSS),” which is publicly available. For this implementation, hash function 414 implements SHA-1, and encryption unit 420 implements the Digital Signature Algorithm (DSA). Processing unit 320 a may also implement some other cryptographic (digital signature or encryption) algorithm, and this is within the scope of the invention.

FIG. 5 shows a processing unit 410 a for generating the signature digest (D) used for the code signature. Processing unit 410 a may be used for hash unit 410 in FIG. 4. Unit 410 a implements Hash-based Message Authentication Code (HMAC). HMAC is described in a document RFC 2104, entitled “HMAC: Keyed-Hashing for Message Authentication,” and in a document FIPS PUB 198, entitled “The Keyed-Hash Message Authentication Code (HMAC),” both of which are publicly available.

Within processing unit 410 a, a unit 512 receives the software ID and performs exclusive-OR of the software ID and an “ipad” value. This ipad value may be the one defined by RFC2401, which is a hexadecimal byte 0×36 repeated 64 times. However, the ipad value may be defined with some other base value instead of 0×36, and the base value may be repeated a different number of times instead of 64 times. The ipad value may also be defined as a single value without any repetition. Zero padding is performed on the software ID and hardware ID as necessary to obtain the desired length, which is not shown in FIG. 5 for simplicity. The exclusive-OR may be performed with a bit-wise modulo-2 add. A concatenate unit 514 receives and concatenates the code digest with the output of ex-OR unit 512 and provides a first message (M1). A hash function 516 receives and hashes the first message and provides a first digest (D1).

A unit 522 performs exclusive-OR of the hardware ID and an “opad” value. This opad value may be the one defined by RFC2401, which is a hexadecimal byte 0×5c repeated 64 times. However, the opad value may be defined with some other base value instead of 0×5c, and the base value may be repeated a different number of times instead of 64 times. The opad value may also be defined as a single value without any repetition. A concatenate unit 518 receives and concatenates the first digest (D1) from hash function 516 with the output of ex-OR unit 522 and provides a second message (M2). A hash function 520 receives and hashes the second message (M2) and provides a second digest, which is used as the signature digest (D). Hash functions 516 and 520 may be implemented with various cryptographic hash functions such as SHA-1, MD-5, or some other hash algorithm.

FIG. 5 shows the use of HMAC in a specific manner to generate the signature digest. The HMAC structure may also be used in other manners to generate the signature digest, and this is within the scope of the invention. For example, the software ID and hardware ID may be concatenated and then provided to unit 512 and exclusive-ORed with the ipad value, and the code digest may be provided to unit 522 and exclusive-ORed with the opad value.

FIGS. 4 and 5 show two exemplary schemes for generating the signature digest. Processing unit 410 a in FIG. 5 uses the three items (i.e., code digest, software ID, and hardware ID) as keys to the HMAC to generate the signature digest. Unit 410 in FIG. 4 concatenates the three items into one message (M) and runs one hash over the message (M) to generate the signature digest. The signature digest may also be generated in other manners, and this is within the scope of the invention.

FIG. 6 shows a flow diagram of a process 600 for generating the code image for the software code. Process 600 is performed by code generator entity 110 and certificate authority 120.

Initially, code generator entity 110 hashes the software code to obtain the code digest (block 612). Code generator entity 110 then sends the code digest, software ID, and hardware ID in a request for a code signature (block 614), which are received by certificate authority 120 (block 622). Certificate authority 120 generates the code signature (if the signature is authorized) for the code digest, the software ID, and the hardware ID using the code private key (block 624). Certificate authority then returns the code signature and certificate (block 626), which are received by code generator entity 110 (block 632). Code generator entity 110 then forms the code image with the software code, software ID, code signature, and certificate, as shown in FIG. 2 (block 634). Code generator entity 110 may thereafter send the code image to wireless device 130 (block 636). The process then terminates.

FIG. 7 shows a flow diagram of a process 700 for generating the code signature. Process 700 includes blocks 622, 624, and 626 in FIG. 6 and further includes a block 710 for authenticating code generator entity 110 and determining whether or not the software code can be associated with the hardware. Process 700 may be performed by certificate authority 120.

Certificate authority 120 receives a request for a code signature from code generator entity 110 (block 622). This request includes the code digest, software ID, hardware ID, and a certificate for code generator entity 110 (which is referred to herein as the “CG certificate”). Certificate authority 120 authenticates code generator entity 110 based on the CG certificate (block 712). If code generator entity 110 is not authenticated based on the CG certificate (i.e., the answer is ‘no’ for block 714), then an error message is sent back (block 720), and the process terminates.

If code generator entity 110 is authenticated (i.e., the answer is ‘yes’ for block 714), then a determination is made whether or not the software represented by the software digest and software ID can be associated with the hardware indicated by the hardware ID (block 716). This may be achieved based on the configuration table maintained by certificate authority 120, as described above. If the software to hardware association is not permitted (i.e., the answer is ‘no’ for block 718), then an error message is sent back (block 720), and the process terminates. Otherwise, certificate authority 120 generates the code signature, as requested, based on the code digest, software ID, and hardware ID (block 624). Certificate authority 120 then sends the code signature and certificate to code generator entity 110 (block 626). The process then terminates.

FIG. 8 shows a block diagram of code generator entity 110, certificate authority 120, and wireless device 130. Code generator entity 110 includes a controller 810, a memory unit 812, and a communication (comm) unit 814. Controller 810 performs processing to generate the code digest and the code image. Memory unit 812 stores the software code as well as program code and data used by controller 810. Communication unit 814 provides communication with certificate authority 120 and wireless device 130.

Certificate authority 120 includes a controller 820, a memory unit 822, and a communication unit 824. Controller 820 performs processing to generate the code signature and certificate. Memory unit 822 stores configuration table 122, crypto keys 124, certificate 126, and program code and data used by controller 820. Communication unit 824 provides communication with code generator entity 110.

Device 130 may communicate with one or more wireless communication systems such as a Code Division Multiple Access (CDMA) system, a Global System for Mobile Communications (GSM) system, a Bluetooth system, a multiple-input multiple-output (MIMO) system, an orthogonal frequency division multiple access (OFDMA) system, and so on. A CDMA system may implement one or more CDMA standards such as IS-2000 (also known as “CDMA 1x-EV”), IS-856 (also known as “CDMA 1x-EVDO”), IS-95, Wideband-CDMA (W-CDMA), and so on. Device 130 is capable of providing bi-directional communication via a receive path and a transmit path.

For the transmit path, a modem processor 850 processes (e.g., encodes and modulates) data to be transmitted by device 130 and provides data chips to a transmitter unit (TMTR) 852. Transmitter unit 852 conditions (e.g., converts to analog, filters, amplifies, and frequency upconverts) the data chips and generates a modulated signal, which is transmitted via an antenna 854. For the receive path, signals transmitted by base stations in one or more systems are received by antenna 854 and provided to a receiver unit (RCVR) 856. Receiver unit 856 conditions (e.g., filters, amplifies, and frequency downconverts) the received signal, digitizes the conditioned signal, and provides data samples to modem processor 850 for demodulation and decoding.

A secure unit 830 performs secure processing and provides secure storage for device 130. For the embodiment shown in FIG. 8, secure unit 830 includes a processor 832 that performs secure processing and possibly other processing, a read only memory (ROM) 834 that stores the boot code, a unit 836 that stores the hardware ID for device 130, and a unit 838 that stores the public key for certificate authority 120. Units 836 and 838 may be implemented with ROMs, fuses, and so on. The boot code in ROM 834, the hardware ID in unit 836, and the CA public key in unit 838 correspond to boot code 134, hardware ID 136, and CA public key 138, respectively, in FIG. 1.

The boot code, hardware ID, and CA public key constitute secure data for device 130 and are stored in a secure manner (e.g., embedded) in one or more secure storage units within secure unit 830. This way, the secure data is safeguarded against security attacks and spoofing entities (e.g., hackers, viruses, and so on) that may attempt to infiltrate secure unit 830 in order to tamper with the secure data. Secure unit 830 may be implemented within a single integrated circuit (IC). Secure unit 830 may also be implemented as a secure and/or tamper resistance unit or module.

Secure unit 830 may be part of an application specific integrated circuit (ASIC) that performs various functions for wireless device 130. For example, the ASIC may include secure unit 830, modem processor 850, and so on. Processor 832 performs secure processing to validate the software code at boot-up. Processor 832 may also perform other functions during normal operation. Thus, processor 832 need not be a dedicated unit that only performs secure processing. For example, processor 832 may itself be the hardware that executes all or portions of the software code and with which the software code is associated.

A controller 840 performs various functions and coordinates and controls the operation of various processing units within device 130. For example, controller 840 may direct modem processor 850 to process data for the transmit and receive paths. A memory unit 842 stores program code and data used by various processing units within device 130. For example, memory unit 842 may store the code image with the software code, software ID, code signature, and certificate. An input/output (I/O) unit 844 provides an interface to external units. For example, I/O unit 844 may provide a mechanism (e.g., a port such as Universal Serial Bus (USB)) for loading the code image to device 130. A bus 862 interconnects various units within device 130.

Device 130 validates the software code within the code image each time the device is powered to ensure that the software code is a valid version. Processor 832 performs the validation based on the boot code stored in ROM 834 and using the hardware ID and CA public key embedded within secure unit 830, as described below. This allows processor 832 to establish trust within wireless device 130 from a known state, which is defined by the boot code, hardware ID, and CA public key. Processor 832 authorizes execution of the software code only after the software has been validated.

FIG. 9 shows a processing unit 900 for validating the software code within the code image based on the code signature. Processing unit 900 may be implemented by processor 832 in FIG. 8. Within unit 900, a hash function 910 receives and hashes the software code from the code image and provides the code digest. Hash function 910 implements the same hash algorithm used for hash function 310 in FIG. 3. A hash function 920 receives and hashes the code digest from hash function 910, the software ID from the code image, and the hardware ID from secure unit 830 and provides a “regenerated” signature digest (D′). Hash function 920 implements the same hash algorithm used for hash unit 410 in FIG. 4.

A decryption unit 930 receives and decrypts the code signature from the code image with the code public key from the certificate and provides the “received” signature digest (D). A compare unit 940 then compares the regenerated signature digest (D′) against the received signature digest (D) and provides a validate flag, which is set to ‘true’ if the two digests match and to ‘false’ otherwise.

FIG. 10 shows a flow diagram of a process 1000 for validating the software code within the code image by wireless device 130. Process 1000 may be performed by processor 832 based on the boot code and is also referred to as a boot-up process.

Initially, the certificate is obtained from the code image and validated using the CA public key that is stored within device 130 (block 1012). The certificate contains the CA signature that was generated with the CA private key of certificate authority 120. This CA signature can be authenticated using the corresponding CA public key that is embedded within secure unit 830. A determination is then made whether or not the CA signature is validated (block 1014). If the answer is ‘no’, then an error message is generated (block 1016), and the boot-up process terminates.

If the CA signature is validated, then the code signature is validated in block 1020. For the code signature validation, the software code is obtained from the code image and hashed using the same hash function 310 used by code generator entity 110 to obtain the code digest (block 1022). The software ID is obtained from the code image and the hardware ID is obtained from secure unit 830. The code digest from block 1022, the software ID, and the hardware ID are then hashed using the same hash function 410 used by certificate authority 120 to obtain the regenerated signature digest (D′) (block 1024).

The code public key is obtained from the certificate and the code signature is obtained from the code image. Since the CA signature is generated over the code public key, the code public key is authenticated if the CA signature is authenticated by the CA public key. The code signature is then decrypted with the code public key to obtain the received signature digest (D), which was used by certificate authority 120 to generate the code signature (block 1026). The received signature digest (D) is then compared against the regenerated signature digest (D′) (block 1028).

A determination is next made whether or not the received signature digest matches the regenerated signature digest (block 1030). If the answer is ‘no’, then an error message is generated (block 1016), and the boot-up process terminates. Otherwise, the software code is indicated as being validated and can be executed (block 1032), and the boot-up process terminates.

The techniques described herein for associating software with hardware may be used for various applications. Some exemplary applications are described below.

One application is for downloading software to a wireless device via an unsecured link. It may be desirable to update the software for the wireless device, for example, to fix bugs, provide new features and functionalities, and so on. The techniques described herein may be used to send new versions of the software via an unsecured communication link (e.g., a wireless link) to the wireless device. The wireless device can validate the received software as originating from a legitimate source and being unmodified using cryptographic techniques, as described above. The wireless device would only execute the software after it has been validated.

Another application is for enforcing authorized (e.g., licensed) use of different hardware platforms. A first entity may have various hardware platforms, with each platform being assigned a different hardware ID. The first entity may grant a second entity licenses for some hardware platforms and no licenses for some other hardware platforms. The licensing information may be stored in the configuration table maintained by certificate authority 120. Whenever the second entity requests a code signature for a particular software and a particular hardware platform, certificate authority 120 would generate the code signature only if the second entity is licensed for the requested hardware platform. This way, a licensee cannot take out a license for a base hardware platform and then try to install and use software on a more elaborate hardware platform.

Yet another application is for enforcing authorized (e.g., licensed) use of a given hardware platform. The hardware for the wireless device may be designed with capability to perform a broad set of functions. These functions may be selectively enabled or disabled by software. Different licenses may be granted for different sets of functions. Each of these sets of functions may be associated with a different software version. The certificate authority may maintain a list of licensees, their specific licenses, and the permitted software version(s) for each licensee. The certificate authority would then generate signatures only for the software code version(s) that have been licensed. In this way, a licensee cannot take out a license for a basic set of functions and then try to install and use software for a more elaborate set of functions.

The techniques described herein for associating software with hardware may be implemented by various means at various entities. For example, these techniques may be implemented with hardware, firmware, software, or a combination thereof. For a hardware implementation, the processing units used to achieve the software with hardware association (at code generator entity 110 and certificate authority 120) and to validate the association (at device 130) may be implemented within application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, micro-controllers, microprocessors, other electronic units designed to perform the functions described herein, or a combination thereof.

For a software implementation, the techniques described herein may be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described herein. The software codes may be stored in memory units (e.g., memory units 812, 822, and 842 in FIG. 8) and executed by processors (e.g., controllers 810, 820, and 840 and processor 832). The memory units may be implemented within the processors or external to the processors, in which case they can be communicatively coupled to the processors via various means as is known in the art.

The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein. 

1. A method of validating software for hardware, comprising: authenticating a certificate with a first public key; obtaining a signature generated for the software, a first identifier for the software, and a second identifier for the hardware, wherein the signature is generated using cryptography and is used to validate an association of the software with the hardware; and validating the signature with a second public key from the certificate, wherein the association of the software with the hardware is validated if the signature is validated.
 2. The method of claim 1, wherein the software is executed by the hardware only if the association is validated.
 3. The method of claim 1, wherein the validating the signature includes hashing information for the software, the first identifier, and the second identifier to obtain a first digest, decrypting the signature with the second public key to obtain a second digest, and comparing the first digest against the second digest, and wherein the signature is validated if the first digest matches the second digest.
 4. The method of claim 3, wherein the validating the signature further includes hashing the software to obtain a third digest used as the information for the software.
 5. The method of claim 1, wherein the signature is generated using a cryptography scheme that includes Hash-based Message Authentication Code (HMAC).
 6. The method of claim 1, wherein the first identifier is a software release version number.
 7. The method of claim 1, wherein the hardware is an integrated circuit of a specific design.
 8. The method of claim 1, wherein the second identifier is a hardware serial number or a part number.
 9. An apparatus operable to validate software for hardware, comprising: a first storage unit configured to store a first public key; and a processor operative to authenticate a certificate with the first public key, obtain a signature generated for the software, a first identifier for the software, and a second identifier for the hardware, wherein the signature is generated using cryptography and is used to validate an association of the software with the hardware, and validate the signature with a second public key from the certificate, wherein the association of the software with the hardware is validated if the signature is validated.
 10. The apparatus of claim 9, wherein the first storage unit is further configured to store the second identifier for the hardware, and wherein the processor is further operative to hash information for the software, the first identifier, and the second identifier from the first storage unit to obtain a first digest, decrypt the signature with the second public key to obtain a second digest, and compare the first digest against the second digest, and wherein the signature is validated if the first digest matches the second digest.
 11. The apparatus of claim 9, further comprising: a second storage unit configured to store boot code executed by the processor to authenticate the certificate and validate the signature.
 12. The apparatus of claim 11, wherein the first and second storage units and the processor are implemented within an integrated circuit.
 13. The apparatus of claim 9 and implemented within a wireless communication device.
 14. An apparatus operable to validate software for hardware, comprising: means for authenticating a certificate with a first public key; means for obtaining a signature generated for the software, a first identifier for the software, and a second identifier for the hardware, wherein the signature is generated using cryptography and is used to validate an association of the software with the hardware; and means for validating the signature with a second public key from the certificate, wherein the association of the software with the hardware is validated if the signature is validated.
 15. The apparatus of claim 14, wherein the means for validating the signature includes means for hashing information for the software, the first identifier, and the second identifier to obtain a first digest, means for decrypting the signature with the second public key to obtain a second digest, and means for comparing the first digest against the second digest, and wherein the signature is validated if the first digest matches the second digest.
 16. A method of associating software with hardware, comprising: obtaining a first identifier for the software; obtaining a second identifier for the hardware; and generating a first signature for the software, the first identifier, and the second identifier using cryptography, wherein the first signature is used to validate an association of the software with the hardware.
 17. The method of claim 16, further comprising: receiving a digest obtained by hashing the software, and wherein the first signature is generated over the digest, the first identifier, and the second identifier.
 18. The method of claim 16, wherein the first signature is generated using a cryptography scheme that includes Hash-based Message Authentication Code (HMAC).
 19. The method of claim 16, further comprising: providing a certificate containing a first public key and a second signature, the first public key corresponding to a first private key used to generate the first signature, and the second signature being generated over the first public key with a second private key for an entity generating the second signature.
 20. The method of claim 16, further comprising: receiving from an entity a request for the first signature; and authenticating the entity prior to generating the first signature.
 21. The method of claim 16, further comprising: determining whether or not association of the software with the hardware is permitted, and wherein the first signature is generated only if the association is permitted.
 22. The method of claim 21, wherein the determining is based on a configuration table of permitted associations between at least one version of software and at least one platform of hardware.
 23. An apparatus operable to associate software with hardware, comprising: a communication unit operative to obtain, from a code generator entity, information for a software code, a first identifier for the software, and a second identifier for the hardware; and a controller operative to generate a signature for the software, the first identifier, and the second identifier using cryptography, wherein the signature is used to validate an association of the software with the hardware.
 24. The apparatus of claim 23, wherein the controller is further operative to determine whether or not association of the software with the hardware is permitted, and to generate the signature only if the association is permitted.
 25. The apparatus of claim 23, wherein the controller is further operative to authenticate the code generator entity prior to generating the signature.
 26. The apparatus of claim 23, further comprising: a memory unit operative to store a configuration table of permitted associations between at least one version of software and at least one platform of hardware, and wherein the controller is further operative to determine whether or not the association of the software with the hardware is permitted based on the configuration table.
 27. An apparatus operable to associate software with hardware, comprising: means for obtaining a first identifier for the software; means for obtaining a second identifier for the hardware; and means for generating a first signature for the software, the first identifier, and the second identifier using cryptography, wherein the first signature is used to validate an association of the software with the hardware.
 28. The apparatus of claim 27, further comprising: means for receiving from an entity a request for the first signature; and means for authenticating the entity prior to generating the first signature.
 29. A method of associating software with hardware, comprising: providing information for the software; providing a first identifier for the software; providing a second identifier for the hardware; receiving a signature generated for the software, the first identifier, and the second identifier, wherein the signature is generated using cryptography and is used to validate an association of the software with the hardware; receiving a certificate containing cryptographic information used to validate the signature; and forming an image comprised of the software, the signature, and the certificate.
 30. The method of claim 29, further comprising: hashing the software to obtain a first digest, and wherein the first digest is provided as the information for the software.
 31. The method of claim 30, wherein the signature is generated using a cryptography scheme that includes Hash-based Message Authentication Code (HMAC), and wherein the HMAC receives the first digest, the first identifier, and the second identifier as inputs and provides a second digest used to generate the signature.
 32. An apparatus operable to associate software with hardware, comprising: a communication unit operative to provide information for the software, a first identifier for the software, and a second identifier for the hardware, receive a signature generated for the software, the first identifier, and the second identifier, wherein the signature is generated using cryptography and is used to validate an association of the software with the hardware, and receive a certificate containing cryptographic information used to validate the signature; and a controller operative to form an image comprised of the software, the signature, and the certificate.
 33. The apparatus of claim 32, wherein the controller is further operative to hash the software to obtain a digest that is provided as the information for the software.
 34. An apparatus operable to associate software with hardware, comprising: means for providing information for the software; means for providing a first identifier for the software; means for providing a second identifier for the hardware; means for receiving a signature generated for the software, the first identifier, and the second identifier, wherein the signature is generated using cryptography and is used to validate an association of the software with the hardware; means for receiving a certificate containing cryptographic information used to validate the signature; and means for forming an image comprised of the software, the signature, and the certificate.
 35. The apparatus of claim 34, further comprising: means for hashing the software to obtain a first digest, and wherein the first digest is provided as the information for the software. 